<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Task Descriptor: Prepare Templates for the Project</title>
<meta name="uma.type" content="TaskDescriptor">
<meta name="uma.name" content="prepare_project_specific_templates">
<meta name="uma.presentationName" content="Prepare Templates for the Project">
<meta name="uma.guid" content="_tBDf0EoeEdqrjq4i3fchvA">
<meta name="element_type" content="TaskDescriptor">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../css/default.css" type="text/css">
<script src="./../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ActivityTreeTable.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ProcessElementPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/processElementData.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var defaultQueryStr = '?proc={659D51DD-DF1F-465E-9F3A-2FC6F9BC7C34}&path={659D51DD-DF1F-465E-9F3A-2FC6F9BC7C34},{A550E1F1-D779-4B1A-9E2C-A364E521A091},_tBDf0EoeEdqrjq4i3fchvA';
					var backPath = './../../';
					var imgPath = './../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, true, true, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top">
<div id="page-guid" value="_tBDf0EoeEdqrjq4i3fchvA"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Task Descriptor: Prepare Templates for the Project</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../images/taskdes_lg_dgm32.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This task describes how to prepare project-specific templates.</td>
</tr>
<tr>
<td>Based on Method Task: <a href="./../../rup/tasks/prepare_project_specific_templates_F4BB56.html" guid="{456ACFD8-B1F7-4B18-ABBE-D58D88C9E7C6}">Prepare Templates for the Project</a></td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Roles</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Main:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_process_engineer_51CC276E.html" guid="_CZ6IcRi2Edq_uI8xTPML6g">流程工程师</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Additional:
								</span></td><td class="sectionTableCell"><span class="sectionTableCellHeading">Assisting:
								</span></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Inputs</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Mandatory:
								</span>
<ul>
<li>None</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Optional:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_tools_F94FDB3.html" guid="_CZ6Idxi2Edq_uI8xTPML6g">工具</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_development_process_BC0297D.html" guid="_CZ6IdBi2Edq_uI8xTPML6g">开发流程</a>
</li>
</ul>
</td><td class="sectionTableCell"><span class="sectionTableCellHeading">External:
								</span>
<ul>
<li>None</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Outputs</th><td class="sectionTableCell" colspan="3">
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_project_specific_templates_D0520B9C.html" guid="_CZ6IeBi2Edq_uI8xTPML6g">特定于项目的模板</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Steps</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="sectionTableCell">
<div class="stepHeading">Identify Templates for the Project </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="IdentifyNeeds" name="IdentifyNeeds"></a> 
<div align="left">
    <table     style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"      bordercolor="#808080" cellspacing="0" cellpadding="4" width="100%" border="1">
        <tbody>
            <tr valign="top">
                <td width="5%">
                    <b>Purpose:</b>
                </td>
                <td width="95%">
                    To identify which templates are needed by the project.
                </td>
            </tr>
        </tbody>
    </table><br />
</div>
<p>
    Based on which work products need to be produced and the formality level required for each work product, identify the
    set of templates that are needed and their format. Preparing templates is considered part of <a class="elementLinkWithUserText" href="./../../rup/tasks/tailor_process_for_project_6CFD05E2.html" guid="{1BA9AAA0-DA89-4C14-B45A-CE28A8A10894}">tailoring the process for the project</a> and the process engineer will
    spend a fair amount of time with the project manager deciding which templates to make available to the teams.
</p>
<p>
    Project-specific templates serve several purposes, including :
</p>
<ul>
    <li>
        To ensure that work products are produced consistently and follow the defined conventions and styles.
    </li>
    <li>
        To describe certain standards required for the project adherence.
    </li>
    <li>
        To get a jump-start on producing work products.
    </li>
</ul>
<p>
    Below is a list of some of the work product types you should consider collecting templates for :
</p>
<ul>
    <li>
        Documents
    </li>
    <li>
        Reports
    </li>
    <li>
        Plans
    </li>
    <li>
        Models
    </li>
    <li>
        Source Code
    </li>
</ul></td>
</tr>
</table>
</div>
<div class="stepHeading">Prepare the Templates for Project Use </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="PrepareTemplates" name="PrepareTemplates"></a> 
<table style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"  bordercolor="#808080" cellspacing="0" cellpadding="4" width="100%" border="1">
    <tbody>
        <tr valign="top">
            <td width="5%">
                <b>Purpose:</b>
            </td>
            <td width="95%">
                To make the identified templates ready to use by the project.
            </td>
        </tr>
    </tbody>
</table>
<p>
    <b>Sub-topics:</b>
</p>
<ul>
    <li>
        <a href="#PrepareObtainExisting">Obtain Existing Templates</a>
    </li>
    <li>
        <a href="#PrepareDevelopNew">Develop New Templates</a>
    </li>
    <li>
        <a href="#PrepareTailor">Tailor the Templates for Project Use</a>
    </li>
    <li>
        <a href="#PrepareMakeAccessible">Make the Templates Accessible</a>
    </li>
</ul>
<h4>
    <a id="PrepareObtainExisting" name="PrepareObtainExisting"></a>Obtain Existing Templates<a href="#PrepareTemplates"><img height="20" alt="To Prepare Templates for project use" src="./../../rup/resources/top.gif"     width="26" border="0" /></a>
</h4>
<p>
    Templates may be available from different sources. Some development organizations keep templates in their asset
    repositories for cross-project reuse. Some projects will make use of the ones shipped with the NUP product. In other
    cases, satisfactory templates might not be available, so the project should consider developing its own.
</p>
<p>
    Templates that ship with the NUP are packaged into two plug-ins that can be included in any NUP configuration built
    using <a class="elementLink" href="./../../rup/tools/rup_rational_method_composer_84A966EC.html" guid="_hAfB8COzEdq41POk0CQYwA">Eclipse Process Framework</a>, and thus be accessible to the project members via the
    published NUP web site. The NUP templates contained in this configuration are listed on the&#160;<a class="elementLink" href="./../../nup_base/customcategories/g_templates_patch_67EDEFF8.html" guid="_ybLSkJ9REd2XnM7YM_dQEQ">NUP模板</a> page.&#160; The
    templates can also be accessed from the "Templates" section of the work product description pages.
</p>
<p>
    Note: A project does not require templates for all of it's work product types. In some cases, a relevant example
    provides equal or better value. Some documentation jobs are best done using tool automation. Document generation tools,
    such as Rational SoDA&trade;, provides lots of ready-made report templates to use for generating reports from project work
    products.
</p>
<h4>
    <a id="PrepareDevelopNew" name="PrepareDevelopNew"></a>Develop New Templates<a href="#PrepareTemplates"><img     height="20" alt="To Prepare Templates for project use" src="./../../rup/resources/top.gif" width="26" border="0" /></a>
</h4>
<p>
    The project management might decide to develop new templates as part of the project if one or more of the identified
    templates is not available or deemed not applicable to the project. This work should be accounted for in project
    planning, assigned to a team member and followed up as you would for the development of any project work product. These
    tasks are often performed on a just-in-time basis, or they might even be a result of transforming a produced work
    product into a template.
</p>
<p>
    The project manager should consider promoting any new or modified templates as candidate assets for future projects.
    This is usually done as part of project assessment work and is often a collaboration with the organization's process
    improvement team.
</p>
<h4>
    <a id="PrepareMakeAccessible" name="PrepareMakeAccessible"></a>Customize the Templates for Project Use <a href="#PrepareTemplates"><img height="20" alt="To Prepare Templates for project use" src="./../../rup/resources/top.gif"     width="26" border="0" /></a>
</h4>
<p>
    Preparing templates for a project includes customizing them to fit the context of the project, and the style of the
    delivery process. Some of the traditional templates that ship with the NUP might be too formal for some types of
    projects, but not formal enough for others. Customizing the collected templates ranges from just inserting the project
    meta-data, such as company name, project code, and logo, to removing or adding complete sections. Most of the NUP
    templates have some process guidance in them, to provide in-document assistance for the production of the work product.
    This text is meant to be erased as the work product evolves. Projects that want all process guidance to be an integral
    part of the NUP web site, can remove this in-document guidance from the templates as part of their customization task.
</p>
<h4>
    <a id="PrepareTailor" name="PrepareTailor"></a>Make the Templates Accessible<a href="#PrepareTemplates"><img     height="20" alt="To Prepare Templates for project use" src="./../../rup/resources/top.gif" width="26" border="0" /></a>
</h4>
<p>
    There are different ways of making templates available to the project members. The most efficient way is to make them
    part of the workspace of the tool you use for the production of the work product, for example, if you use Rational
    Rose&trade; for designing the system, then it is desirable that your model template appears as a selection when you select to
    create a new model file. Different applications have different ways of handling this integration. Refer to the on-line
    help of the application for further details. Regardless of whether its possible to achieve this level of integration,
    it is valuable to make the templates part of your project-specific process web site to allow the team members to browse
    and inspect the templates.
</p>
<p>
    The NUP templates are packaged as method plug-ins, and can be included in your method configuration by selecting one or
    more of these plug-ins in <a class="elementLink" href="./../../rup/tools/rup_rational_method_composer_84A966EC.html" guid="_hAfB8COzEdq41POk0CQYwA">Eclipse Process Framework</a>.&#160; You can also make your own templates available using
    the plug-in technology. For more information on plug-ins and configurations, see <a class="elementLinkWithType" href="./../../rup/guidances/concepts/tailoring_rup_F8F0EB23.html" guid="6.991505672198195E-305">Concept: 定制 NUP</a>.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Maintain Templates </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="MaintainTemplates" name="MaintainTemplates"></a> 
<table style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"  bordercolor="#808080" cellspacing="0" cellpadding="4" width="100%" border="1">
    <tbody>
        <tr valign="top">
            <td width="5%">
                <b>Purpose:</b>
            </td>
            <td width="95%">
                To improve the templates based on the consumers experience of use.
            </td>
        </tr>
    </tbody>
</table>
<p>
    In any reuse focussed organization, it is critical to the process improvement effort that projects provide feedback on
    their use of assets. Remember that most good practices generally become good because they've been used a number of
    times before and have had time to be fine-tuned and improved.
</p>
<p>
    As the templates are instantiated and the work products evolve, the project members are likely to identify improvement
    areas for the templates. A project might choose to modify the template or raise a change request for it to be handled
    outside the project, depending on the complexity of the required change. Most projects will benefit from updating the
    templates as needed, and promoting the improved template to the organization's process group as part of the process
    improvement effort.
</p><br />
<br /></td>
</tr>
</table>
</div>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Properties</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Multiple Occurrences" abbr="Multiple Occurrences">Multiple Occurrences</th><td class="sectionTableCell" align="left" headers="property_Multiple Occurrences"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Event Driven" abbr="Event Driven">Event Driven</th><td class="sectionTableCell" align="left" headers="property_Event Driven"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Ongoing" abbr="Ongoing">Ongoing</th><td class="sectionTableCell" align="left" headers="property_Ongoing"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Optional" abbr="Optional">Optional</th><td class="sectionTableCell" align="left" headers="property_Optional"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Planned" abbr="Planned">Planned</th><td class="sectionTableCell" align="left" headers="property_Planned"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Repeatable" abbr="Repeatable">Repeatable</th><td class="sectionTableCell" align="left" headers="property_Repeatable"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script language="JavaScript" type="text/javascript">
					contentPage.onload();
					contentPage.processPage.fixDescriptorLinks();
				</script>
</html>
